Security News
Research
Supply Chain Attack on Rspack npm Packages Injects Cryptojacking Malware
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
State management with error handling and reactive cache done right.
Alternative standalone implementation of eigenmethod mol_atom.
Usage examples with reactive-di: example source, demo, todomvc benchmark
Install npm install --save lom_atom
import {mem} from 'lom_atom'
class Todo {
@mem title = ''
}
const todo = new Todo()
todo.title = '123'
import {mem} from 'lom_atom'
class Todo {
@mem set title(next: string) {
// test next
}
@mem get title(): string {
return 'default'
}
}
const todo = new Todo()
todo.title = '123'
Killer feature, grabbed from mol_atom. We can reset cache on get or obviously set cache value, using magic force property.
On set value: force mode talk lom to pass value through set handler. On get value: invoke handler with undefined, true
and reset cache.
import {force, mem} from 'lom_atom'
class TodoList {
@force force: TodoList
@mem set todos(todos: Todo | Error) {
console.log('set handler')
}
@mem get todos() {
console.log('get handler')
return [someTodo]
}
}
const list = new TodoList()
list.todos = [someTodo] // console: set handler
list.todos = [someTodo] // someTodo already set - no handler call
list.force.todos = [someTodo] // force, console: set handler
list.todos // console: get handler
list.todos // return cached value
list.force.todos // console: get handler
In this form we can change value on set. Less magic, than regular properties.
import {action, mem} from 'lom_atom'
class Some {
@force $: Some
@mem name(next?: string, force?: boolean): string {
// if next !== undefined - set mode
if (next !== undefined) return next
return 'default value'
}
}
const some = new Some()
some.name() === 'default value'
some.name('new value') // Set value directly into atom cache, some.name() handler not called
some.name() === 'new value'
some.name('val', true) // Pass value through some.name() handler and set result into cache
some.name(undefined, true) === 'default value' // Invoke some.name() handler and reset to default value
some.force.name(val)
alias of some.name(val, true)
And some.force.name()
alias of some.name(undefined, true)
One decorator for all cases.
class TodoList {
@mem todos = []
@mem get unfinishedTodos() {
return this.todos.filter((todo) => !todo.finished)
}
}
Like mobx, unfinishedTodos is updated automatically when a todo changed.
Like mobx reaction produces a side effect for making network requests, etc. But side effects in lom are simpler.
Listener.listen throws errors on todo list store property access, if todo list loading finished with erorr or loading in progress.
class TodoList {
@mem set todos(todos: Todo | Error) {}
@mem get todos() {
// Side effect, cached in mem
fetch('/todos')
.then((todos) => {
this.todos = todos
})
.catch(e => this.todos = e)
throw new mem.Wait()
}
@mem get unfinishedTodos() {
return this.todos.filter((todo) => !todo.finished)
}
}
class Listener {
_list = new TodoList()
@mem listen() {
try {
console.log('total todos:', this._list.todos.length)
console.log('unfinished todos:', this._list.unfinishedTodos.length)
} catch (e) {
if (e instanceof mem.Wait) {
console.log('loading...')
} else {
console.error('error', e.message)
}
}
}
}
const listener = new Listener()
listener.listen()
Basic dictionary support. First argument is an key of any type. See eigenmethod mol_mem.
class TodoList {
@mem.key todo(id: string, next?: Todo, force?: boolean): Todo {
if (next === undefined) {
return {}
}
return next
}
}
const list = new TodoList()
list.todo('1', {id: 1, title: 'Todo 1'}) // set todo
list.todo('1') // get todo
State updates are asynchronous, but sometime we need to do transactional synced updates via action helper:
import {action, mem} from 'lom_atom'
class Some {
@mem name = ''
@mem id = ''
@action set(id: string, name: string) {
this.id = id
this.name = name
}
}
const some = new Some()
// Transactionally changed in current tick:
action(() => {
some.name = 'test'
some.id = '123'
})
// or
some.set('123', 'test')
1.1.4 (2017-09-27)
<a name="1.1.3"></a>
FAQs
Alternative implementation of eigenmethod mol_atom state management library
The npm package lom_atom receives a total of 7 weekly downloads. As such, lom_atom popularity was classified as not popular.
We found that lom_atom demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.
Security News
Sonar’s acquisition of Tidelift highlights a growing industry shift toward sustainable open source funding, addressing maintainer burnout and critical software dependencies.